Your data has issues
There is a problem
- 1000 entries must have valid geometry
| Reference | Name | Tree preservation order | Uprn | Address text | Point | Geometry | Notes | Felled date | Entry date | Start date | End date |
|---|---|---|---|---|---|---|---|---|---|---|---|
| 751 | K52 | 217107377 | EGERTON CRESCENT |
POINT (-0.16779 51.49545) Unexpected geom type |
2025-01-03 | ||||||
| 752 | Oct-73 | 217027697 | EGERTON CRESCENT |
POINT (-0.1683 51.4947) Unexpected geom type |
2025-01-03 | ||||||
| 753 | Oct-73 | 217027698 | EGERTON CRESCENT |
POINT (-0.16827 51.49474) Unexpected geom type |
2025-01-03 | ||||||
| 754 | Oct-73 | 217027702 | EGERTON CRESCENT |
POINT (-0.16792 51.49489) Unexpected geom type |
2025-01-03 | ||||||
| 755 | Oct-73 | 217027706 | EGERTON CRESCENT |
POINT (-0.16758 51.495) Unexpected geom type |
2025-01-03 | ||||||
| 756 | Oct-73 | 217027725 | EGERTON CRESCENT |
POINT (-0.16715 51.49604) Unexpected geom type |
2025-01-03 | ||||||
| 757 | Oct-73 | 217027726 | EGERTON CRESCENT |
POINT (-0.1671 51.49609) Unexpected geom type |
2025-01-03 | ||||||
| 758 | Oct-73 | 217027727 | EGERTON CRESCENT |
POINT (-0.16707 51.49614) Unexpected geom type |
2025-01-03 | ||||||
| 759 | Oct-73 | 217027728 | EGERTON CRESCENT |
POINT (-0.167 51.49619) Unexpected geom type |
2025-01-03 | ||||||
| 760 | Oct-73 | 217027724 | EGERTON CRESCENT |
POINT (-0.1672 51.49599) Unexpected geom type |
2025-01-03 | ||||||
| 761 | Sep-70 | 217027728 | EGERTON CRESCENT |
POINT (-0.167 51.49619) Unexpected geom type |
2025-01-03 | ||||||
| 762 | Jan-99 | 217027728 | EGERTON CRESCENT |
POINT (-0.167 51.49619) Unexpected geom type |
2025-01-03 | ||||||
| 763 | 4/00 | 217027710 | EGERTON CRESCENT |
POINT (-0.16734 51.49518) Unexpected geom type |
2025-01-03 | ||||||
| 764 | 08-Jan | 217027688 | EGERTON CRESCENT |
POINT (-0.16836 51.49462) Unexpected geom type |
2025-01-03 | ||||||
| 765 | 07-Feb | 217027711 | EGERTON CRESCENT |
POINT (-0.16728 51.49523) Unexpected geom type |
2025-01-03 | ||||||
| 766 | 12-Feb | 217027714 | EGERTON CRESCENT |
POINT (-0.16718 51.4954) Unexpected geom type |
2025-01-03 | ||||||
| 767 | K52 | 217107350 | EGERTON GARDENS |
POINT (-0.16812 51.49619) Unexpected geom type |
2025-01-03 | ||||||
| 768 | K52 | 217027836 | EGERTON GARDENS |
POINT (-0.16872 51.49534) Unexpected geom type |
2025-01-03 | ||||||
| 769 | Oct-72 | 217028151 | EGERTON PLACE |
POINT (-0.16659 51.49633) Unexpected geom type |
2025-01-03 | ||||||
| 770 | K53 | 217107351 | EGERTON PLACE |
POINT (-0.16674 51.49682) Unexpected geom type |
2025-01-03 | ||||||
| 771 | Oct-73 | 217028151 | EGERTON PLACE |
POINT (-0.16659 51.49633) Unexpected geom type |
2025-01-03 | ||||||
| 772 | K52 | 217028177 | EGERTON TERRACE |
POINT (-0.16687 51.49594) Unexpected geom type |
2025-01-03 | ||||||
| 773 | K52 | 217028178 | EGERTON TERRACE |
POINT (-0.16686 51.49584) Unexpected geom type |
2025-01-03 | ||||||
| 774 | K53 | 217028167 | EGERTON TERRACE |
POINT (-0.16633 51.49627) Unexpected geom type |
2025-01-03 | ||||||
| 775 | K53 | 217028175 | EGERTON TERRACE |
POINT (-0.16573 51.49591) Unexpected geom type |
2025-01-03 | ||||||
| 776 | Oct-73 | 217028179 | EGERTON TERRACE |
POINT (-0.1667 51.49585) Unexpected geom type |
2025-01-03 | ||||||
| 777 | Oct-73 | 217028185 | EGERTON TERRACE |
POINT (-0.16637 51.49564) Unexpected geom type |
2025-01-03 | ||||||
| 778 | Oct-73 | 217028186 | EGERTON TERRACE |
POINT (-0.16626 51.49561) Unexpected geom type |
2025-01-03 | ||||||
| 779 | Oct-73 | 217028174 | EGERTON TERRACE |
POINT (-0.16581 51.49596) Unexpected geom type |
2025-01-03 | ||||||
| 780 | Oct-73 | 217028172 | EGERTON TERRACE |
POINT (-0.16595 51.49603) Unexpected geom type |
2025-01-03 | ||||||
| 781 | Oct-73 | 217028170 | EGERTON TERRACE |
POINT (-0.1661 51.49612) Unexpected geom type |
2025-01-03 | ||||||
| 782 | Oct-73 | 217028169 | EGERTON TERRACE |
POINT (-0.16617 51.49616) Unexpected geom type |
2025-01-03 | ||||||
| 783 | Oct-72 | 217028188 | ELDON ROAD |
POINT (-0.18692 51.49766) Unexpected geom type |
2025-01-03 | ||||||
| 784 | K44 | 217028187 | ELDON ROAD |
POINT (-0.18685 51.49765) Unexpected geom type |
2025-01-03 | ||||||
| 785 | Oct-72 | 217028189 | ELDON ROAD |
POINT (-0.18701 51.49766) Unexpected geom type |
2025-01-03 | ||||||
| 786 | K44 | 217028193 | ELDON ROAD |
POINT (-0.18717 51.49766) Unexpected geom type |
2025-01-03 | ||||||
| 787 | K44 | 217028196 | ELDON ROAD |
POINT (-0.18744 51.49765) Unexpected geom type |
2025-01-03 | ||||||
| 788 | K44 | 217028197 | ELDON ROAD |
POINT (-0.18751 51.49766) Unexpected geom type |
2025-01-03 | ||||||
| 789 | Oct-72 | 217028198 | ELDON ROAD |
POINT (-0.18759 51.49766) Unexpected geom type |
2025-01-03 | ||||||
| 790 | K44 | 217028199 | ELDON ROAD |
POINT (-0.18769 51.49765) Unexpected geom type |
2025-01-03 | ||||||
| 791 | Oct-72 | 217028202 | ELDON ROAD |
POINT (-0.18793 51.49765) Unexpected geom type |
2025-01-03 | ||||||
| 792 | K44 | 217028204 | ELDON ROAD |
POINT (-0.18809 51.49766) Unexpected geom type |
2025-01-03 | ||||||
| 793 | K44 | 217028206 | ELDON ROAD |
POINT (-0.18668 51.49798) Unexpected geom type |
2025-01-03 | ||||||
| 794 | K44 | 217028208 | ELDON ROAD |
POINT (-0.18693 51.49799) Unexpected geom type |
2025-01-03 | ||||||
| 795 | K44 | 217028216 | ELDON ROAD |
POINT (-0.18717 51.49799) Unexpected geom type |
2025-01-03 | ||||||
| 796 | K44 | 217028217 | ELDON ROAD |
POINT (-0.18731 51.49799) Unexpected geom type |
2025-01-03 | ||||||
| 797 | Oct-72 | 217028222 | ELDON ROAD |
POINT (-0.18776 51.498) Unexpected geom type |
2025-01-03 | ||||||
| 798 | Oct-72 | 217028224 | ELDON ROAD |
POINT (-0.18798 51.49801) Unexpected geom type |
2025-01-03 | ||||||
| 799 | K44 | 217028225 | ELDON ROAD |
POINT (-0.18808 51.49801) Unexpected geom type |
2025-01-03 | ||||||
| 800 | 13-Jan | 217028217 | ELDON ROAD |
POINT (-0.18731 51.49799) Unexpected geom type |
2025-01-03 |
Showing rows 751 to 800 of 1000
How to fix this issue
Your data is missing a geometry.
The tree guidance explains how to fix the issue:
geometry
The boundary of the tree as a single polygon or multipolygon value. All points in the polygon must be in the WGS84 coordinate reference system.
If you’re providing geometry in a CSV, geometry should be in well-known text (WKT).
You must provide a point or geometry for each tree. You may provide both.
Example: MULTIPOLYGON (((1.188829 51.23478,1.188376 51.234909,1.188381 51.234917,1.187912 51.235022...
If you’re providing geometry in a GeoJSON, GML or Geopackage, use the associated geometry format.
How to improve Royal Borough of Kensington and Chelsea’s data
- Fix the errors indicated
- Use the check service to make sure the data meets the standard
- Publish the updated data on the endpoint URL